1 simulated user executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.
3 simulated users executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.
4 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~27s). Sessions should end around the same time as each other for consistent behavior.
21 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~27s). Sessions should end around the same time as each other for consistent behavior.
Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.
Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.
Total HTTP and supporting files (JS/CSS) latency (load time) is displayed for each session and run combination. Each vertical bar represents the amount of time a session's Shiny application had to wait before it is able to ask the server for information. A resonable amount of time to wait as been set to 5s. Warmup and cooldown sessions are displayed outside the dotted maintenance period lines.
Maximum WebSocket latency (calculation time) is displayed for each session and run combination. The maximum time is shown to convey the longest amount of time a user would have to wait for a response from the Shiny server. Warmup and cooldown sessions are displayed outside the dotted maintenance period lines.
Event plots are arranged by the slowest maximum time within each plot.
slowest maximum times
Event plots are arranged by the slowest minimum time within each plot.
slowest minimum times
Event plots are arranged by the largest difference in the run's mean event time.
largest mean differences
| Label | Max time | Min time | Mean Difference |
|---|---|---|---|
| Event 16) Updated: distPlot | 3.373 | 3.033 | 0.076 |
| Event 17) Updated: distPlot | 3.112 | 3.030 | 0.012 |
| Event 22) Completed File Upload | 3.046 | 0.007 | 0.182 |
| Event 20) Post Request | 1.307 | 0.383 | 0.389 |
| Event 15) Updated: distPlot | 0.976 | 0.460 | 0.277 |
| Event 1) Get: Homepage | 0.520 | 0.190 | 0.013 |
| Event 23) Updated: contents | 0.450 | 0.234 | 0.055 |
| Event 7) Start Session | 0.272 | 0.125 | 0.010 |
| Event 5) Get: Shiny Token | 0.267 | 0.136 | 0.003 |
| Event 6) Get: Connection Information | 0.253 | 0.120 | 0.012 |
| Event 3) Get: rstudio-connect.css | 0.242 | 0.139 | 0.004 |
| Event 4) Get: shiny-server-client.min.js | 0.227 | 0.128 | 0.002 |
| Event 2) Get: sockjs.min.js | 0.220 | 0.127 | 0.019 |
| Event 10) Updated: | 0.150 | 0.003 | 0.010 |
| Event 12) Initialize Session | 0.132 | 0.000 | 0.027 |
| Event 19) File Upload | 0.061 | 0.005 | 0.004 |
| Event 8) Start Connection | 0.026 | 0.000 | 0.004 |
| Event 24) Stop Session | 0.003 | 0.000 | 0.001 |
| Event 9) SockJS Initialize Connection | 0.001 | 0.000 | 0.000 |
| Event 13) Initialize Inputs | 0.001 | 0.000 | 0.000 |
| Event 14) Set: bins | 0.001 | 0.000 | 0.000 |
| Event 18) Start File Upload | 0.001 | 0.000 | 0.000 |
| Event 21) Stop File Upload: | 0.001 | 0.000 | 0.000 |
| Event 11) Set: file1:shiny.file, bins, sep, quote, disp, header | 0.000 | 0.000 | 0.000 |
Event plots are arranged by the largest slope magnitude found when fitting a line to each run.
largest slope magnitudes
Event plots are arranged by the largest intercept magnitude found when fitting a line to each run
largest intercept magnitudes
Event plots are arranged by the largest error magnitude found when fitting a line to each run.
largest error magnitudes
| Label | Slope | Intercept | Error |
|---|---|---|---|
| Event 22) Completed File Upload | 0.305 | -0.604 | 2.735 |
| Event 20) Post Request | -0.066 | 0.848 | 0.459 |
| Event 5) Get: Shiny Token | 0.041 | 0.185 | 0.079 |
| Event 23) Updated: contents | 0.038 | 0.390 | 0.114 |
| Event 1) Get: Homepage | 0.036 | 0.291 | 0.237 |
| Event 3) Get: rstudio-connect.css | 0.029 | 0.175 | 0.066 |
| Event 7) Start Session | 0.028 | 0.186 | 0.090 |
| Event 2) Get: sockjs.min.js | 0.026 | 0.191 | 0.049 |
| Event 10) Updated: | 0.017 | -0.030 | 0.129 |
| Event 19) File Upload | -0.010 | 0.046 | 0.036 |
| Event 4) Get: shiny-server-client.min.js | 0.009 | 0.186 | 0.057 |
| Event 16) Updated: distPlot | -0.004 | 3.165 | 0.285 |
| Event 6) Get: Connection Information | 0.004 | 0.166 | 0.079 |
| Event 8) Start Connection | 0.004 | 0.008 | 0.018 |
| Event 17) Updated: distPlot | 0.004 | 3.050 | 0.054 |
| Event 12) Initialize Session | 0.003 | 0.063 | 0.095 |
| Event 13) Initialize Inputs | 0.000 | -0.001 | 0.001 |
| Event 18) Start File Upload | 0.000 | -0.000 | 0.001 |
| Event 21) Stop File Upload: | -0.000 | 0.001 | 0.001 |
| Event 9) SockJS Initialize Connection | 0.000 | 0.000 | 0.001 |
| Event 24) Stop Session | -0.000 | 0.002 | 0.001 |
| Event 11) Set: file1:shiny.file, bins, sep, quote, disp, header | -0.000 | -0.000 | 0.000 |
| Event 14) Set: bins | 0.000 | 0.001 | |
| Event 15) Updated: distPlot | 0.781 | 0.230 |